-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix dead lock in multi DB when using batchUpdate(#31038) #31118
Conversation
2b82310
to
7622e69
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You can wait for Fixes nativeTest failure under GraalVM Native Image due to class information changes #31320 to be merged and then rebase to the master branch. Failure of nativeTest is expected and requires the fix of Fixes nativeTest failure under GraalVM Native Image due to class information changes #31320 .
|
I have rebased the master branch |
|
I am sorry,just misoperation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The PR did not pass the code formatting validation. You can execute first
./mvnw spotless:apply -Pcheck -T1C
. Then execute./mvnw checkstyle:check -Pcheck -T1C
to manually adjust to repair the CI.
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You need to change the
org.apache.shardingsphere.test.natived.jdbc.commons.TestShardingService#processSuccessInClickHouse()
. Reference https://github.com/apache/shardingsphere/actions/runs/9387875307/job/25852084140?pr=31118#step:4:53356 .
Failures (1):
JUnit Jupiter:ClickHouseTest:assertShardingInLocalTransactions()
MethodSource [className = 'org.apache.shardingsphere.test.natived.jdbc.databases.ClickHouseTest', methodName = 'assertShardingInLocalTransactions', methodParameterTypes = '']
=> java.lang.AssertionError:
Expected: <[1, 1, 1, 1, 1, 0, 0, 0, 0, 0]>
but: was <[0, 0, 0, 0, 0, 1, 1, 1, 1, 1]>
org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8)
org.apache.shardingsphere.test.natived.jdbc.commons.TestShardingService.processSuccessInClickHouse(TestShardingService.java:100)
org.apache.shardingsphere.test.natived.jdbc.databases.ClickHouseTest.assertShardingInLocalTransactions(ClickHouseTest.java:47)
[email protected]/java.lang.reflect.Method.invoke(Method.java:580)
[email protected]/java.util.ArrayList.forEach(ArrayList.java:1596)
[email protected]/java.util.ArrayList.forEach(ArrayList.java:1596)
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- This PR indeed explains some phenomena that have existed before and does affect some integration tests. From my perspective, there doesn't seem to be any significant issue with the current PR at this point. I'll await the completion of the CI process.
Thank you for your recognition. |
Fixes #31038.
Changes proposed in this pull request:
Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.